elliptic-curve: use Cargo.toml for array/bigint imports#2160
Merged
tarcieri merged 1 commit intoDec 29, 2025
Merged
Conversation
Names them `array` and `bigint` in `Cargo.toml`, using the `package` field to refer to `hybrid-array` and `crypto-bigint` respectively. This means they're consistently referred to as `array` and `bigint` from within the crate, and should also help diagnostics that sometimes get confused and refer to e.g. `elliptic_curve::crypto_bigint` using the previous approach of `pub use crypto_bigint as bigint`.
tarcieri
changed the title
Cargo.toml for array/bigint` importsCargo.toml for array/bigint imports
tarcieri
deleted the
elliptic-curve/use-cargo-toml-for-array-and-bigint-imports
branch
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Names them
arrayandbigintinCargo.toml, using thepackagefield to refer tohybrid-arrayandcrypto-bigintrespectively.This means they're consistently referred to as
arrayandbigintfrom within the crate, and should also help diagnostics that sometimes get confused and refer to e.g.elliptic_curve::crypto_bigintusing the previous approach ofpub use crypto_bigint as bigint.